System and method for handling peripheral connections to mobile devices

ABSTRACT

Systems and methods for establishing a data connection between a mobile device and a peripheral. The mobile device is configured to determine whether to handle user approval of the data connection between the mobile device and the peripheral. Through the mobile device, an input mechanism is provided for the user to provide input. The input is used in determining whether to approve the data connection between the mobile device and the peripheral.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 15/336,437 filed Oct. 27, 2016 by Michael Kenneth Brown, etal., entitled “System and Method for Handling Peripheral Connections toMobile Devices”, which is a continuation of U.S. Pat. No. 9,507,950issued on Nov. 29, 2016, which is a continuation of U.S. Pat. No.8,447,696 issued on May 21, 2013, which is a continuation of U.S. Pat.No. 7,664,707 issued on Feb. 16, 2010, which claims priority to andbenefit of U.S. Provisional Application No. 60/566,774 filed Apr. 30,2004 by Neil P. Adams et al., entitled “System and Method for HandlingPeripheral Connections to Mobile Devices”, all of which are incorporatedby reference herein as if reproduced in their entirety.

BACKGROUND

The present invention relates generally to the field of communications,and in particular to data connections to mobile wireless communicationsdevices.

Mobile wireless communications devices typically allow peripherals(e.g., a desktop computer) to connect to the devices. When a peripheralis installed, a connection between a mobile device and a peripheral canbe opened, and data is then allowed to be transferred between the two.

Because of security reasons and other reasons, typically the connectionis to be approved by the device's user before data can be transferred.As an illustration, if the connection is not approved, an attacker couldmount the following attack. If the user has a Trojan horse applicationon their handheld, then an attacker can pickpocket the device, attach alaptop, connect with the Trojan horse application, and then theapplication can transfer the user's data from the device or inject arogue application. Accordingly, some type of approval should be usedwhen dealing with peripherals for mobile devices.

In accordance with the teachings disclosed herein, systems and methodsare provided for establishing a data connection between a mobile deviceand a peripheral. As an example of a system and method, the mobiledevice is configured to determine whether it is to handle user approvalof the data connection between the mobile device and the peripheral.Through the mobile device, an input mechanism is provided for the userto provide input. The input is used in determining whether to approvethe data connection between the mobile device and the peripheral.

As another example, an apparatus can include connection handler dataprocessing instructions configured to determine, on the mobile device,that the mobile device is to handle user approval of the data connectionbetween the mobile device and the peripheral. Output instructions can beconfigured to provide through the mobile device a prompt to the user forthe user to provide input. The connection handler instructions can beconfigured to determine whether to approve the data connection betweenthe mobile device and the peripheral based upon the user input.

As will be appreciated, the systems and methods disclosed herein arecapable of other and different embodiments, and capable of modificationsin various respects. Accordingly, the drawings and description set forthherein are to be regarded as illustrative in nature and not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overview of an example communication system in which awireless communication device may be used.

FIG. 2 is a block diagram of a further example communication systemincluding multiple networks and multiple mobile communication devices.

FIGS. 3 and 4 are block diagrams depicting attempts to establish a dataconnection between a mobile device and a peripheral.

FIGS. 5 and 6 are flowcharts depicting an operational scenario forestablishing a data connection between a peripheral and a mobile device.

FIG. 7 is a block diagram depicting an operational scenario forestablishing a data connection between a peripheral and a mobile devicewhich is in a locked state.

FIG. 8 is a block diagram of an example mobile device.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overview of an example communication system in which awireless communication device may be used. One skilled in the art willappreciate that there may be hundreds of different topologies, but thesystem shown in FIG. 1 helps demonstrate the operation of the encodedmessage processing systems and methods described in the presentapplication. There may also be many message senders and recipients. Thesimple system shown in FIG. 1 is for illustrative purposes only, andshows perhaps the most prevalent Internet e-mail environment wheresecurity is not generally used.

FIG. 1 shows an e-mail sender 10, the Internet 20, a message serversystem 40, a wireless gateway 85, wireless infrastructure 90, a wirelessnetwork 105 and a mobile communication device 100.

An e-mail sender system 10 may, for example, be connected to an ISP(Internet Service Provider) on which a user of the system 10 has anaccount, located within a company, possibly connected to a local areanetwork (LAN), and connected to the Internet 20, or connected to theInternet 20 through a large ASP (application service provider) such asAmerica Online (AOL). Those skilled in the art will appreciate that thesystems shown in FIG. 1 may instead be connected to a wide area network(WAN) other than the Internet, although e-mail transfers are commonlyaccomplished through Internet-connected arrangements as shown in FIG. 1.

The message server 40 may be implemented, for example, on a networkcomputer within the firewall of a corporation, a computer within an ISPor ASP system or the like, and acts as the main interface for e-mailexchange over the Internet 20. Although other messaging systems mightnot require a message server system 40, a mobile device 100 configuredfor receiving and possibly sending e-mail will normally be associatedwith an account on a message server. Perhaps the two most common messageservers are Microsoft Exchange™ and Lotus Domino™. These products areoften used in conjunction with Internet mail routers that route anddeliver mail. These intermediate components are not shown in FIG. 1, asthey do not directly play a role in the secure message processingdescribed below. Message servers such as server 40 typically extendbeyond just e-mail sending and receiving; they also include dynamicdatabase storage engines that have predefined database formats for datalike calendars, to-do lists, task lists, e-mail and documentation.

The wireless gateway 85 and infrastructure 90 provide a link between theInternet 20 and wireless network 105. The wireless infrastructure 90determines the most likely network for locating a given user and tracksthe user as they roam between countries or networks. A message is thendelivered to the mobile device 100 via wireless transmission, typicallyat a radio frequency (RF), from a base station in the wireless network105 to the mobile device 100. The particular network 105 may bevirtually any wireless network over which messages may be exchanged witha mobile communication device.

As shown in FIG. 1, a composed e-mail message 15 is sent by the e-mailsender 10, located somewhere on the Internet 20. This message 15 isnormally fully in the clear and uses traditional Simple Mail TransferProtocol (SMTP), RFC822 headers and Multipurpose Internet Mail Extension(MIME) body parts to define the format of the mail message. Thesetechniques are all well known to those skilled in the art. The message15 arrives at the message server 40 and is normally stored in a messagestore. Most known messaging systems support a so-called “pull” messageaccess scheme, wherein the mobile device 100 must request that storedmessages be forwarded by the message server to the mobile device 100.Some systems provide for automatic routing of such messages which areaddressed using a specific e-mail address associated with the mobiledevice 100. In a preferred embodiment described in further detail below,messages addressed to a message server account associated with a hostsystem such as a home computer or office computer which belongs to theuser of a mobile device 100 are redirected from the message server 40 tothe mobile device 100 as they are received.

Regardless of the specific mechanism controlling the forwarding ofmessages to the mobile device 100, the message 15, or possibly atranslated or reformatted version thereof, is sent to the wirelessgateway 85. The wireless infrastructure 90 includes a series ofconnections to wireless network 105. These connections could beIntegrated Services Digital Network (ISDN), Frame Relay or T1connections using the TCP/IP protocol used throughout the Internet. Asused herein, the term “wireless network” is intended to include threedifferent types of networks, those being (1) data-centric wirelessnetworks, (2) voice-centric wireless networks and (3) dual-mode networksthat can support both voice and data communications over the samephysical base stations. Combined dual-mode networks include, but are notlimited to, (1) Code Division Multiple Access (CDMA) networks, (2) theGroupe Special Mobile or the Global System for Mobile Communications(GSM) and the General Packet Radio Service (GPRS) networks, and (3)future third-generation (3G) networks like Enhanced Data-rates forGlobal Evolution (EDGE) and Universal Mobile Telecommunications Systems(UMTS). Some older examples of data-centric network include the Mobitex™Radio Network and the DataTAC™ Radio Network. Examples of oldervoice-centric data networks include Personal Communication Systems (PCS)networks like GSM, and TDMA systems.

FIG. 2 is a block diagram of a further example communication systemincluding multiple networks and multiple mobile communication devices.The system of FIG. 2 is substantially similar to the FIG. 1 system, butincludes a host system 30, a redirection program 45, a mobile devicecradle 65, a wireless virtual private network (VPN) router 75, anadditional wireless network 110 and multiple mobile communicationdevices 100. As described above in conjunction with FIG. 1, FIG. 2represents an overview of a sample network topology. Although theencoded message processing systems and methods described herein may beapplied to networks having many different topologies, the network ofFIG. 2 is useful in understanding an automatic e-mail redirection systemmentioned briefly above.

The central host system 30 will typically be a corporate office or otherLAN, but may instead be a home office computer or some other privatesystem where mail messages are being exchanged. Within the host system30 is the message server 40, running on some computer within thefirewall of the host system, that acts as the main interface for thehost system to exchange e-mail with the Internet 20. In the system ofFIG. 2, the redirection program 45 enables redirection of data itemsfrom the server 40 to a mobile communication device 100. Although theredirection program 45 is shown to reside on the same machine as themessage server 40 for ease of presentation, there is no requirement thatit must reside on the message server. The redirection program 45 and themessage server 40 are designed to co-operate and interact to allow thepushing of information to mobile devices 100. In this installation, theredirection program 45 takes confidential and non-confidential corporateinformation for a specific user and redirects it out through thecorporate firewall to mobile devices 100. A more detailed description ofthe redirection software 45 may be found in the commonly assigned U.S.Pat. No. 6,219,694 (“the '694 Patent”), entitled “System and Method forPushing Information From A Host System To A Mobile Data CommunicationDevice Having A Shared Electronic Address”, and issued to the assigneeof the instant application on Apr. 17, 2001, which is herebyincorporated into the present application by reference. This pushtechnique may use a wireless friendly encoding, compression andencryption technique to deliver all information to a mobile device, thuseffectively extending the security firewall to include each mobiledevice 100 associated with the host system 30.

As shown in FIG. 2, there may be many alternative paths for gettinginformation to the mobile device 100. One method for loading informationonto the mobile device 100 is through a port designated 50, using adevice cradle 65. This method tends to be useful for bulk informationupdates often performed at initialization of a mobile device 100 withthe host system 30 or a computer 35 within the system 30. The other mainmethod for data exchange is over-the-air using wireless networks todeliver the information. As shown in FIG. 2, this may be accomplishedthrough a wireless VPN router 75 or through a traditional Internetconnection 95 to a wireless gateway 85 and a wireless infrastructure 90,as described above. The concept of a wireless VPN router 75 is new inthe wireless industry and implies that a VPN connection could beestablished directly through a specific wireless network 110 to a mobiledevice 100. The possibility of using a wireless VPN router 75 has onlyrecently been available and could be used when the new Internet Protocol(IP) Version 6 (IPV6) arrives into IP-based wireless networks. This newprotocol will provide enough IP addresses to dedicate an IP address toevery mobile device 100 and thus make it possible to push information toa mobile device 100 at any time. A principal advantage of using thiswireless VPN router 75 is that it could be an off-the-shelf VPNcomponent, thus it would not require a separate wireless gateway 85 andwireless infrastructure 90 to be used. A VPN connection would preferablybe a Transmission Control Protocol (TCP)/IP or User Datagram Protocol(UDP)/IP connection to deliver the messages directly to the mobiledevice 100. If a wireless VPN 75 is not available then a link 95 to theInternet 20 is the most common connection mechanism available and hasbeen described above.

In the automatic redirection system of FIG. 2, a composed e-mail message15 leaving the e-mail sender 10 arrives at the message server 40 and isredirected by the redirection program 45 to the mobile device 100. Asthis redirection takes place the message 15 is re-enveloped, asindicated at 80, and a possibly proprietary compression and encryptionalgorithm can then be applied to the original message 15. In this way,messages being read on the mobile device 100 are no less secure than ifthey were read on a desktop workstation such as 35 within the firewall.All messages exchanged between the redirection program 45 and the mobiledevice 100 preferably use this message repackaging technique. Anothergoal of this outer envelope is to maintain the addressing information ofthe original message except the sender's and the receiver's address.This allows reply messages to reach the appropriate destination, andalso allows the “from” field to reflect the mobile user's desktopaddress. Using the user's e-mail address from the mobile device 100allows the received message to appear as though the message originatedfrom the user's desktop system 35 rather than the mobile device 100.

With reference back to the port 50 and cradle 65 connectivity to themobile device 100, this connection path offers many advantages forenabling one-time data exchange of large items. For those skilled in theart of personal digital assistants (PDAs) and synchronization, the mostcommon data exchanged over this link is Personal Information Management(PIM) data 55. When exchanged for the first time this data tends to belarge in quantity, bulky in nature and requires a large bandwidth to getloaded onto the mobile device 100 where it can be used on the road. Thisserial link may also be used for other purposes, including setting up aprivate security key 111 such as an S/MIME or PGP specific private key,the Certificate (Cert) of the user and their Certificate RevocationLists (CRLs) 60. The private key is preferably exchanged so that thedesktop 35 and mobile device 100 share one personality and one methodfor accessing all mail. The Cert and CRLs are normally exchanged oversuch a link because they represent a large amount of the data that isrequired by the device for S/MIME, PGP and other public key securitymethods.

FIG. 3 depicts a mobile device 100 and a peripheral device 200attempting to establish a connection 210 between themselves. Theconnection 210 is intended to allow data to be transferred between thedevices (100, 200). Some examples of peripherals 200 are:

a personal computer (e.g., a desktop or laptop computer) in order to do,among other things, backup/restore or synchronization operations.

a smart card reader in order to do two factor authentication andsecurity operations.

a memory card.

a hardware crypto token.

a camera.

etc.

The connection 210 can involve a physical connection or a wirelessconnection with a peripheral. As an example, a connection 210 can be aUSB (universal serial bus) connection, wherein a USB cable is attachedto the USB ports of each device. Data transfer between the devices canoccur after the USB connection is approved by a user (e.g., a mobiledevice can store and/or retrieve data stored on a peripheral memorycard).

Before a connection 210 can be opened, a user 220 is to approve theconnection 210, such as by typing their handheld password 232 via theperipheral's computer-human interface (e.g., desktop computer's keyboardand display screen). Once the password 232 is verified with the mobiledevice 100, the connection 210 is opened and data can be transferred.This mechanism for authenticating the desktop to the device (i.e., thehandheld owner is the one using the desktop) works because the desktophas an output device (e.g., a screen) to prompt the user 220 to entertheir password and an input device (e.g., a keyboard) to allow the user220 to enter their password.

If a peripheral 200 cannot provide a prompt (as indicated at 230) and/orobtain input (as indicated at 232) from a user 220 in order to obtainconnection approval, then the connection 210 can be established as shownin FIG. 4. With reference to FIG. 4, when a peripheral 200 is connectedto the mobile device 100, the peripheral 200 is given the opportunity tosupply connection-related input (e.g., a handheld password). If theperipheral 200 can supply the password, then the peripheral 200 isallowed to open a connection. However, if the peripheral 200 cannotsupply the password (e.g., because it does not have a mechanism for theuser to supply it), then the peripheral 200 can request that theconnection approval process be redirected to the mobile device 100.

As shown at 300, the user 220 is then prompted on the mobile device 100for their handheld password 310 in order to allow a connection 210 to beopened by the peripheral 200. If the user 220 knows the password 310 andsupplies it to the mobile device 100, a connection 210 is opened withthe peripheral 200, otherwise the connection 210 is refused. If the userdoes not have a handheld password 310 set on their mobile device 100,the user may just be notified that a connection approval is needed andasked to approve the opening of the connection 210 by the peripheral200, without the user having to supply a password 310.

FIGS. 5 and 6 depict an operational scenario 400 for establishing a dataconnection between a peripheral and a mobile device. At step 402, aperipheral device is connected to a mobile device, such as through a USBcable or a wireless connection such as an infrared device or a Bluetoothconnection, but the connection is not opened.

Decision step 404 examines whether the peripheral can obtain and supplythe mobile device's password. If the peripheral can and the password isvalid, then as indicated at step 406, the connection for transferringdata is allowed, and processing for this operational scenario terminatesat end block 408. However, if the peripheral cannot supply the mobiledevice's password (e.g., the password is invalid), then the peripheralprovides at step 410 an indication to the mobile device to acquire theuser input for allowing the data connection. Processing continues onFIG. 6 as indicated by continuation marker 412.

With reference to FIG. 6, the mobile device attempts to acquire thepassword from the user at step 414. The mobile device can acquire thisinformation from the user by generating a message prompt on the mobiledevice's user interface. The message prompt could ask the user for thedevice's password. The message prompt may also contain an input field inwhich the user can type via the mobile device's keyboard a passwordentry.

If the user provides a valid password as determined at decision step416, then the data transfer connection is allowed, and the device andperipheral can interact. Processing for this operational scenarioterminates at end block 422.

If the user does not provide a valid password as determined at decisionstep 416, then the data transfer connection is not allowed, andprocessing for this operational scenario terminates at end block 422.

As illustrated by this operational scenario, the chance of a Trojanhorse attack is reduced because the attacker also must know the handheldpassword. It also enhances a mobile device's support for peripherals,because it allows peripherals to be connected that on their own cannotsupply the handheld password.

It should be understood that similar to the other processing flowsdescribed herein, the steps and the order of the steps in the flowchartdescribed herein may be altered, modified and/or augmented and stillachieve the desired outcome. For example, at step 414, when entering thepassword, the user could be restricted by the same policy setting aswhen the user would be entering the device's password independent of aperipheral data connection scenario. The memory contents of the mobiledevice can be wiped if their password is entered incorrectly apredetermined number of times. Also, the password they are typing may ormay not be shown depending on password policy settings. As anotherexample, many different types of approval indication inputs can beprovided by the user in addition to or in place of a handheld'spassword.

FIG. 7 illustrates an operational scenario wherein the mobile device 100is in a locked state. If the mobile device 100 is locked when theperipheral 200 is inserted into the device 100 or otherwise connected tothe device 100, the user 220 may not be asked for their handheldpassword explicitly. This prevents the prompting 500 of the user 220 fortheir password 502 too often. When the user 220 unlocks their mobiledevice 100, they enter their handheld password, and through that act,they are implicitly allowing any currently connected peripheral 200 toopen a connection 210. In this way, lock-related input 502 can be usedfor multiple purposes: (1) to unlock the mobile device 100; and (2) toapprove the connection 210.

The systems and methods disclosed herein are presented only by way ofexample and are not meant to limit the scope of the invention. Othervariations of the systems and methods described above will be apparentto those skilled in the art and as such are considered to be within thescope of the invention. For example, the systems and methods disclosedherein may be used with many different computers and devices, such as awireless mobile communications device shown in FIG. 8. With reference toFIG. 8, the mobile device 100 is a dual-mode mobile device and includesa transceiver 611, a microprocessor 638, a display 622, non-volatilememory 624, random access memory (RAM) 626, one or more auxiliaryinput/output (I/O) devices 628, a serial port 630, a keyboard 632, aspeaker 634, a microphone 636, a short-range wireless communicationssub-system 640, and other device sub-systems 642.

The transceiver 611 includes a receiver 612, a transmitter 614, antennas616 and 618, one or more local oscillators 613, and a digital signalprocessor (DSP) 620. The antennas 616 and 618 may be antenna elements ofa multiple-element antenna, and are preferably embedded antennas.However, the systems and methods described herein are in no wayrestricted to a particular type of antenna, or even to wirelesscommunication devices.

The mobile device 100 is preferably a two-way communication devicehaving voice and data communication capabilities. Thus, for example, themobile device 100 may communicate over a voice network, such as any ofthe analog or digital cellular networks, and may also communicate over adata network. The voice and data networks are depicted in FIG. 8 by thecommunication tower 619. These voice and data networks may be separatecommunication networks using separate infrastructure, such as basestations, network controllers, etc., or they may be integrated into asingle wireless network.

The transceiver 611 is used to communicate with the network 619, andincludes the receiver 612, the transmitter 614, the one or more localoscillators 613 and the DSP 620. The DSP 620 is used to send and receivesignals to and from the antennas 616 and 618, and also provides controlinformation to the receiver 612 and the transmitter 614. If the voiceand data communications occur at a single frequency, or closely-spacedsets of frequencies, then a single local oscillator 613 may be used inconjunction with the receiver 612 and the transmitter 614.Alternatively, if different frequencies are utilized for voicecommunications versus data communications for example, then a pluralityof local oscillators 613 can be used to generate a plurality offrequencies corresponding to the voice and data networks 619.Information, which includes both voice and data information, iscommunicated to and from the transceiver 611 via a link between the DSP620 and the microprocessor 638.

The detailed design of the transceiver 611, such as frequency band,component selection, power level, etc., will be dependent upon thecommunication network 619 in which the mobile device 100 is intended tooperate. For example, a mobile device 100 intended to operate in a NorthAmerican market may include a transceiver 611 designed to operate withany of a variety of voice communication networks, such as the Mobitex orDataTAC mobile data communication networks, AMPS, TDMA, CDMA, PCS, etc.,whereas a mobile device 100 intended for use in Europe may be configuredto operate with the GPRS data communication network and the GSM voicecommunication network. Other types of data and voice networks, bothseparate and integrated, may also be utilized with a mobile device 100.

Depending upon the type of network or networks 619, the accessrequirements for the mobile device 100 may also vary. For example, inthe Mobitex and DataTAC data networks, mobile devices are registered onthe network using a unique identification number associated with eachmobile device. In GPRS data networks, however, network access isassociated with a subscriber or user of a mobile device. A GPRS devicetypically requires a subscriber identity module (“SIM”), which isrequired in order to operate a mobile device on a GPRS network. Local ornon-network communication functions (if any) may be operable, withoutthe SIM device, but a mobile device will be unable to carry out anyfunctions involving communications over the data network 619, other thanany legally required operations, such as ‘911’ emergency calling.

After any required network registration or activation procedures havebeen completed, the mobile device 100 may the send and receivecommunication signals, including both voice and data signals, over thenetworks 619. Signals received by the antenna 616 from the communicationnetwork 619 are routed to the receiver 612, which provides for signalamplification, frequency down conversion, filtering, channel selection,etc., and may also provide analog to digital conversion. Analog todigital conversion of the received signal allows more complexcommunication functions, such as digital demodulation and decoding to beperformed using the DSP 620. In a similar manner, signals to betransmitted to the network 619 are processed, including modulation andencoding, for example, by the DSP 620 and are then provided to thetransmitter 614 for digital to analog conversion, frequency upconversion, filtering, amplification and transmission to thecommunication network 619 via the antenna 618.

In addition to processing the communication signals, the DSP 620 alsoprovides for transceiver control. For example, the gain levels appliedto communication signals in the receiver 612 and the transmitter 614 maybe adaptively controlled through automatic gain control algorithmsimplemented in the DSP 620. Other transceiver control algorithms couldalso be implemented in the DSP 620 in order to provide moresophisticated control of the transceiver 611.

The microprocessor 638 preferably manages and controls the overalloperation of the mobile device 100. Many types of microprocessors ormicrocontrollers could be used here, or, alternatively, a single DSP 620could be used to carry out the functions of the microprocessor 638.Low-level communication functions, including at least data and voicecommunications, are performed through the DSP 620 in the transceiver611. Other, high-level communication applications, such as a voicecommunication application 624A, and a data communication application624B may be stored in the non-volatile memory 624 for execution by themicroprocessor 638. For example, the voice communication module 624A mayprovide a high-level user interface operable to transmit and receivevoice calls between the mobile device 100 and a plurality of other voiceor dual-mode devices via the network 619. Similarly, the datacommunication module 624B may provide a high-level user interfaceoperable for sending and receiving data, such as e-mail messages, files,organizer information, short text messages, etc., between the mobiledevice 100 and a plurality of other data devices via the networks 619.

The microprocessor 638 also interacts with other device subsystems, suchas the display 622, the RAM 626, the auxiliary input/output (I/O)subsystems 628, the serial port 630, the keyboard 632, the speaker 634,the microphone 636, the short-range communications subsystem 640 and anyother device subsystems generally designated as 642.

Some of the subsystems shown in FIG. 8 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as the keyboard 632 and thedisplay 622 may be used for both communication-related functions, suchas entering a text message for transmission over a data communicationnetwork, and device-resident functions such as a calculator or task listor other PDA type functions.

Operating system software used by the microprocessor 638 is preferablystored in a persistent store such as non-volatile memory 624. Thenon-volatile memory 624 may be implemented, for example, as a Flashmemory component, or as battery backed-up RAM. In addition to theoperating system, which controls low-level functions of the mobiledevice 610, the non-volatile memory 624 includes a plurality of softwaremodules 624A-624N that can be executed by the microprocessor 638 (and/orthe DSP 620), including a voice communication module 624A, a datacommunication module 624B, and a plurality of other operational modules624N for carrying out a plurality of other functions. These modules areexecuted by the microprocessor 638 and provide a high-level interfacebetween a user and the mobile device 100. This interface typicallyincludes a graphical component provided through the display 622, and aninput/output component provided through the auxiliary I/O 628, keyboard632, speaker 634, and microphone 636. The operating system, specificdevice applications or modules, or parts thereof, may be temporarilyloaded into a volatile store, such as RAM 626 for faster operation.Moreover, received communication signals may also be temporarily storedto RAM 626, before permanently writing them to a file system located ina persistent store such as the Flash memory 624.

An exemplary application module 624N that may be loaded onto the mobiledevice 100 is a personal information manager (PIM) application providingPDA functionality, such as calendar events, appointments, and taskitems. This module 624N may also interact with the voice communicationmodule 624A for managing phone calls, voice mails, etc., and may alsointeract with the data communication module for managing e-mailcommunications and other data transmissions. Alternatively, all of thefunctionality of the voice communication module 624A and the datacommunication module 624B may be integrated into the PIM module.

The non-volatile memory 624 preferably also provides a file system tofacilitate storage of PIM data items on the device. The PIM applicationpreferably includes the ability to send and receive data items, eitherby itself, or in conjunction with the voice and data communicationmodules 624A, 624B, via the wireless networks 619. The PIM data itemsare preferably seamlessly integrated, synchronized and updated, via thewireless networks 619, with a corresponding set of data items stored orassociated with a host computer system, thereby creating a mirroredsystem for data items associated with a particular user.

Context objects representing at least partially decoded data items, aswell as fully decoded data items, are preferably stored on the mobiledevice 100 in a volatile and non-persistent store such as the RAM 626.Such information may instead be stored in the non-volatile memory 624,for example, when storage intervals are relatively short, such that theinformation is removed from memory soon after it is stored. However,storage of this information in the RAM 626 or another volatile andnon-persistent store is preferred, in order to ensure that theinformation is erased from memory when the mobile device 100 losespower. This prevents an unauthorized party from obtaining any storeddecoded or partially decoded information by removing a memory chip fromthe mobile device 100, for example.

The mobile device 100 may be manually synchronized with a host system byplacing the device 100 in an interface cradle, which couples the serialport 630 of the mobile device 100 to the serial port of a computersystem or device. The serial port 630 may also be used to enable a userto set preferences through an external device or software application,or to download other application modules 624N for installation. Thiswired download path may be used to load an encryption key onto thedevice, which is a more secure method than exchanging encryptioninformation via the wireless network 619. Interfaces for other wireddownload paths may be provided in the mobile device 100, in addition toor instead of the serial port 630. For example, a USB port would providean interface to a similarly equipped personal computer.

Additional application modules 624N may be loaded onto the mobile device100 through the networks 619, through an auxiliary I/O subsystem 628,through the serial port 630, through the short-range communicationssubsystem 640, or through any other suitable subsystem 642, andinstalled by a user in the non-volatile memory 624 or RAM 626. Suchflexibility in application installation increases the functionality ofthe mobile device 100 and may provide enhanced on-device functions,communication-related functions, or both. For example, securecommunication applications may enable electronic commerce functions andother such financial transactions to be performed using the mobiledevice 100.

When the mobile device 100 is operating in a data communication mode, areceived signal, such as a text message or a web page download, isprocessed by the transceiver module 611 and provided to themicroprocessor 638, which preferably further processes the receivedsignal in multiple stages as described above, for eventual output to thedisplay 622, or, alternatively, to an auxiliary I/O device 628. A userof mobile device 100 may also compose data items, such as e-mailmessages, using the keyboard 632, which is preferably a completealphanumeric keyboard laid out in the QWERTY style, although otherstyles of complete alphanumeric keyboards such as the known DVORAK stylemay also be used. User input to the mobile device 100 is furtherenhanced with a plurality of auxiliary I/O devices 628, which mayinclude a thumbwheel input device, a touchpad, a variety of switches, arocker input switch, etc. The composed data items input by the user maythen be transmitted over the communication networks 619 via thetransceiver module 611.

When the mobile device 100 is operating in a voice communication mode,the overall operation of the mobile device is substantially similar tothe data mode, except that received signals are preferably be output tothe speaker 634 and voice signals for transmission are generated by amicrophone 636. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on the mobiledevice 100. Although voice or audio signal output is preferablyaccomplished primarily through the speaker 634, the display 622 may alsobe used to provide an indication of the identity of a calling party, theduration of a voice call, or other voice call related information. Forexample, the microprocessor 638, in conjunction with the voicecommunication module and the operating system software, may detect thecaller identification information of an incoming voice call and displayit on the display 622.

A short-range communications subsystem 640 is also included in themobile device 100. The subsystem 640 may include an infrared device andassociated circuits and components, or a short-range RF communicationmodule such as a Bluetooth™ module or an 802.11 module, for example, toprovide for communication with similarly-enabled systems and devices.Those skilled in the art will appreciate that “Bluetooth” and “802.11”refer to sets of specifications, available from the Institute ofElectrical and Electronics Engineers, relating to wireless personal areanetworks and wireless local area networks, respectively.

The systems' and methods' data may be stored in one or more data stores.The data stores can be of many different types of storage devices andprogramming constructs, such as RAM, ROM, Flash memory, programming datastructures, programming variables, etc. It is noted that data structuresdescribe formats for use in organizing and storing data in databases,programs, memory, or other computer-readable media for use by a computerprogram.

The systems and methods may be provided on many different types ofcomputer-readable media including computer storage mechanisms (e.g.,CD-ROM, diskette, RAM, flash memory, computer's hard drive, etc.) thatcontain instructions for use in execution by a processor to perform themethods' operations and implement the systems described herein.

The computer components, software modules, functions and data structuresdescribed herein may be connected directly or indirectly to each otherin order to allow the flow of data needed for their operations. It isalso noted that a module or processor includes but is not limited to aunit of code that performs a software operation, and can be implementedfor example as a subroutine unit of code, or as a software function unitof code, or as an object (as in an object-oriented paradigm), or as anapplet, or in a computer script language, or as another type of computercode.

What is claimed is:
 1. A method for establishing a data connectionbetween a peripheral device and a mobile device, the method comprising:receiving, by the mobile device, an indication from the peripheraldevice for user approval of the data connection; prompting, by themobile device, for a user input in response to receiving the indication,wherein prompting for the user input comprises prompting a user of themobile device to provide an input regarding the user approval of thedata connection; determining, by the mobile device, whether to establishthe data connection in response to receiving the user input; andapproving or rejecting establishment of the data connection based onverification of the user input.
 2. The method of claim 1, wherein theuser input comprises one of a password or other approval indication. 3.The method of claim 1, wherein the indication is received responsive tothe peripheral device connecting to the mobile device via a physicalconnection or a wireless connection.
 4. The method of claim 3, whereinthe peripheral device connects to the mobile device physically via auniversal serial bus (USB) cable or wirelessly via a Bluetooth protocol.5. The method of claim 1, further comprising: receiving, by the mobiledevice, the indication from the peripheral device while the mobiledevice is in a locked state; and refraining, by the mobile device, fromprompting for the user input until the mobile device is unlocked by theuser of the mobile device.
 6. The method of claim 1, wherein the userinput comprises a password, and wherein determining, by the mobiledevice, whether to establish the data connection based on the user inputfurther comprises: approving establishment of the data connection whenthe password is valid; and rejecting establishment of the dataconnection when the password is not valid.
 7. The method of claim 6,wherein establishing the data connection comprises opening a datatransfer connection between the peripheral device and the mobile device.8. The method of claim 1, wherein the peripheral device is unable toprovide a prompt to the user or to obtain the input from the user. 9.The method of claim 1, wherein the peripheral device is one of a smartcard reader, a memory card, a hardware cryptographic-related token, or acamera.
 10. The method of claim 1, wherein the mobile device is a mobilewireless communications device.
 11. A non-transitory computer readablemedium storing computer readable instructions that, when executed by aprocessor, implement a method for establishing a data connection betweena peripheral device and a mobile device, comprising: receiving anindication redirecting user approval of the data connection from theperipheral device to the mobile device; prompting a user of the mobiledevice for a user input in response to receiving the indication, whereinprompting for the user input comprises prompting a user of the mobiledevice to provide an input regarding the user approval of the dataconnection; determining, by the mobile device, whether to establish thedata connection in response to receiving the user input; and approvingor rejecting establishment of the data connection based on verificationof the user input.
 12. The non-transitory computer readable medium ofclaim 11, wherein the user input comprises one of a password or otherapproval indication.
 13. The non-transitory computer readable medium ofclaim 11, wherein the user input comprises a password, and whereindetermining whether to establish the data connection based on the userinput further comprises: approving establishment of the data connectionwhen the password is valid; and rejecting establishment of the dataconnection when the password is not valid.
 14. The non-transitorycomputer readable medium of claim 13, wherein establishing the dataconnection comprises opening a data transfer connection between theperipheral device and the mobile device.
 15. The non-transitory computerreadable medium of claim 11, wherein the method further comprises:receiving the indication from the peripheral device while the mobiledevice is in a locked state; and refraining, by the mobile device, fromprompting for the user input until the mobile device is unlocked by theuser of the mobile device.
 16. A mobile device for establishing a dataconnection with a peripheral device, the mobile device comprising: amemory device; and a processor configured to execute instructions storedon the memory device such that when executed, cause the mobile deviceto: receive an indication from the peripheral device for user approvalof the data connection; prompt a user of the mobile device for a userinput in response to receiving the indication, wherein prompting for theuser input comprises prompting the user to provide an input regardingthe user approval of the data connection; determine whether to establishthe data connection in response to receiving the user input; and approveor reject establishment of the data connection based on verification ofthe user input.
 17. The mobile device of claim 16, wherein the userinput comprises one of a password or other approval indication.
 18. Themobile device of claim 16, wherein the user input comprises a password,and wherein determining whether to establish the data connection basedon the user input further comprises: approving establishment of the dataconnection when the password is valid; and rejecting establishment ofthe data connection when the password is not valid.
 19. The mobiledevice of claim 18, wherein establishing the data connection comprisesopening a data transfer connection between the peripheral device and themobile device.
 20. The mobile device of claim 16, wherein when theindication is received while the mobile device is in a locked state, themobile device refrains from prompting for the user until the mobiledevice is unlocked by the user of the mobile device.